Conversation
|
One thing I notice is the cli command is very long with this functionality added, maybe SSL certs should be passed as environment vars or added to the script as global constants? e.g. python ssl.py --ca_file /etc/contrail/ssl/certs/ca-cert.pem --cert_file /etc/contrail/ssl/certs/server.pem --key_file /etc/contrail/ssl/private/server-privkey.pem vr intf |
|
|
Hi @pinggit I'll answer point (2) first. These env or cli options are completely optional. If they are not specified the script will run as you initially designed it. See below, this is a non SSL backend: |
|
Now point (1): So you enable SSL support in one of two ways:
The location of the certs Contrail uses is configured in /etc/contrail so if you are running the script on the server itself you can get them from: However if you are running from a remote host, you would need to have a cert / key pair that is signed by the same CA as the certs installed on the Contrail servers |
|
hi @dannyvernals , thanks! |
|
Hey @pinggit sorry I miss-understood. With juju deployment this pretty simple: For other deployments I'm not sure, maybe creating a self signed cert & CA manually on the compute host and pointing contrail at them with env vars? cat /etc/contrail/common_vrouter.env | egrep "SERVER_|SSL_ENABLE" |
|
thanks Danny! I tested the script with ssl support in my setup without enabling the ssl, and I don't see a problem. |
|
Hi @pinggit yes that makes sense. The process you would follow is:
FYI, these are the config changes that were made by juju on an agent (vrouter): |
I've been testing ist.py on SSL enabled hosts so I needed to add passing certs and key file to requests.
Please let me know what you think